Skip to content

Only export LIBCLANG_PATH when override=true#36

Closed
chrysn wants to merge 2 commits intoesp-rs:mainfrom
chrysn-pull-requests:libclang-path-override
Closed

Only export LIBCLANG_PATH when override=true#36
chrysn wants to merge 2 commits intoesp-rs:mainfrom
chrysn-pull-requests:libclang-path-override

Conversation

@chrysn
Copy link
Contributor

@chrysn chrysn commented Feb 16, 2025

Closes: #35

This is the simple approach (reusing the override tunable); discussion in #35 will need to show whether that is an acceptable change, or whether a new tunable is needed.

@chrysn chrysn force-pushed the libclang-path-override branch from 9eb1ad3 to df455f1 Compare February 16, 2025 12:25
This is primarily useful for hands-off environments where the paths are
not exported by default (otherwise, downstream actions would need to
hard-code this action's choice of export file), and conveniently allows
eliding the parameter during installation (because the variable is used
by espup).
@chrysn chrysn mentioned this pull request Feb 17, 2025
@chrysn
Copy link
Contributor Author

chrysn commented Feb 17, 2025

Closing this in favor of #38 -- that one does appear cleaner and is not really much more effort to maintain.

@chrysn chrysn closed this Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

LIBCLANG_PATH is set unconditionally

1 participant